applyingFiltering() no longer works as expected.

I notice that code that was working before, is no longer working.
Specifically, applyingFiltering().

If I reduce it to this:

Module m = current
bool FilterStatus = applyingFiltering (m)
                if (FilterStatus)
                {
                        errorBox "Filter On"
                        halt            //terminates execution
                } // end if (FilterStatus)
print "FilterStatus " FilterStatus "\n"

it returns false every time when a filter is on.

When I originally coded this script, it worked, returning true when the filter was present.

Any suggestions?

Thank you

Gedinfo - Wed Jun 13 16:27:16 EDT 2012

Re: applyingFiltering() no longer works as expected.
llandale - Wed Jun 13 16:51:34 EDT 2012

applyingFiltering 
Declaration 
bool applyingFiltering(Module) 
 
Operation 
Returns a boolean indicating whether filtering is turned on in the module explorer for the specified module.

Not sure what "filtering the module explorer" means, but perhaps that's the issue.

-Louie

Re: applyingFiltering() no longer works as expected.
Gedinfo - Thu Jun 14 10:30:16 EDT 2012

I found a function 'filtering' which performs as expected.

Returns false when a module is not filtered,
true when it is being filtered.

Re: applyingFiltering() no longer works as expected.
llandale - Thu Jun 14 16:03:39 EDT 2012

Gedinfo - Thu Jun 14 10:30:16 EDT 2012
I found a function 'filtering' which performs as expected.

Returns false when a module is not filtered,
true when it is being filtered.

Did a little lookup. The "applyFiltering" and "applyingFiltering" and "unApplyFiltering" refer to filters on the Module Explorer (something I hadn't actually considered). (applyFiltering makes the Explorer match the objects). "filter on/off" and "filtering" refer to filtering the objects themselves.

So "applyingFiltering" would be the same as "filtering" when you "filter on; applyFiltering"

-Louie